-
-
Notifications
You must be signed in to change notification settings - Fork 818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove info from ExecutionParams and add operationType #3166
Conversation
🦋 Changeset detectedLatest commit: 5a8093d The changes in this PR will be included in the next version bump. This PR includes changesets to release 25 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest changes of this PR are available as alpha in npm (based on the declared
|
See #3180 (comment) I guess I think it’s ok as is for now do you feel strongly about this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ardatan what's the background for this change?
1c0e83c
to
e84ca74
Compare
e84ca74
to
e834e8a
Compare
@yaacovCR Updated this PR. If you want to discuss the changes individually, I can split this into smaller PRs. |
aac64ac
to
eae68dd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to allow operationType to be optional and inferred from document (rather than info!) if absent.
I think it may in theory be still useful as well when stitching to allow info to be passed to executor just like context.
Other than those points, love it.
BREAKING CHANGES;
Request
toExecutionRequest
(Request
is also part of DOM types so this prevents the possible confusion)GraphQLResolveInfo
inExecutionRequest
operationType: OperationTypeNode
as a required field inExecutionRequest
context
increateRequest
andcreateRequestInfo
instead ofdelegateToSchema
Improvements;
defaultExecutor
for a singleGraphQLSchema
so allowgetBatchingExecutor
to memoizebatchingExecutor
correctly.defaultExecutor
is created forsubscription
and other operation types. Only one executor is used.